🦋 Changeset detected

Latest commit: cea398a

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

✅ Deploy Preview for red-hat-design-system ready!

Name	Link
🔨 Latest commit	cea398a
🔍 Latest deploy log	https://app.netlify.com/sites/red-hat-design-system/deploys/67631a616293c300080f6dca
😎 Deploy Preview	https://deploy-preview-2069--red-hat-design-system.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Size Change: +496 B (+0.24%)

Total Size: 208 kB

_{compressed-size-action}

Looks like this aria-live approach does work in Firefox with VO, but it does not work in Safari or Edge. I added aria-atomic="true" hoping that would fix it. Alas, no joy.

When adding aria-live content to the lightdom, it gets announced. WDYT about adding the <div aria-live="polite"> there?

i'll try refactoring to using a single, global, visually hidden aria-live region appended to the document body

On OSX 15.1.1 with VO, this is working in the following browsers:

• Edge
• Safari
• Chrome
• Firefox

@hellogreg could we possibly tap you to test screen readers in Windows and maybe iOS/Android?

@bennypowers can you confirm this works in Linux?

If everything works there, that would be 👏 .

Results with orca on wayland (fedora silverblue)
✔️ ff works
❌ epiphany (WebKit, gnome web) doesn't announce tooltip content
👎 chromium doesn't work with orca at all, not just for this pr

i think live regions don't work at all for orca and WebKit, at least not on my setup: https://codepen.io/bennyp/pen/MYgJVdR?editors=1001

So all things considered I think we can approve this as best effort - when the browser bugs resolve it will work, and we can't work around it

This comment/issue is not related to changes in this PR, but it looks like there is an issue with positioning calculation in the left demo where the tooltip is both in a dir="rtl" and style="text-align: right" styled parent. My assumption is this is related to RTL support of floating-dom controller. I will break this out into a new issue and track it separately.

Feedback from Greg says that this (mostly) works across various screen readers—which is much better than it not working at all.

So all things considered I think we can approve this as best effort

I agree with this. PTAL and thanks everyone for your help and feedback.

Feedback from Greg says that this (mostly) works across various screen readers—which is much better than it not working at all.

Yep, we're at least getting something from all the major browser/reader combos, even if there are some quirks with, say, Android TalkBack/Chrome and Windows Narrator/Edge.